…-project

Yarn 4 changed the pnpm linker's .store subdirectory name to 'package/'
(was the package name in yarn 3), breaking path-based hook detection.

Switch the main project to nodeLinker: node-modules to avoid the issue,
and add test/pnpm-compat/ as a minimal independent yarn sub-project with
nodeLinker: pnpm to specifically test the pnpm linker path format support.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

…kiness

The "mapping a script using async tracking timeout 10" test was flaky on
Node.js 18: instead of the expected timeout=10 event ordering it produced
the timeout=0 ordering, as if async tracking buffering had never engaged.
The test passes on Node.js 20, 22, and 24.

Hypothesis: timers/promises.setTimeout creates an internal Timeout async
resource that overrides the AsyncLocalStorage context on Node.js 18 when
the timer fires, causing Recording.buffer to fall back to rootBuffer.
Since rootBuffer was ≥10ms old at that point, passEventsAndClearBuffer
flushed all buffered events before getMessage reached the stream. Using
`new Promise(resolve => globalThis.setTimeout(resolve, 100))` avoids the
internal Timeout resource — the Promise is created inside asyncStorage.run
so its continuation should inherit the correct context on all Node versions.